Even if the mirrors list says something isn't supported, check it anyway. 🔼

Sometimes the mirror list gets out of sync with reality, so test reality, then mark the reports with any differences.


For the class of issues "HTTPS supported but not listed":

ATM the list is maintained manually, so if changes are not

notified, they are not reflected. The list was updated with this

class of issues unless I missed some.  

For things like this I'll be saying "https: [N/A]", which will mean the

mirror list says it's not supported.  So just as this email prompted

some mirror admins to say "hey, we do support HTTPS now", this should

prompt similar reports, and thus we can manually update the list.

Maybe I could test HTTPS anyway, then report "https: [OK, fix list]" or

some such.

...

The official mirror list says "temporarily-offline", so my

mirror

checker doesn't bother to check it.  I should probably add an

option to

check it anyway, so the admin of this mirror knows what works

and what

doesn't.  

It was removed of the RR because it was being problematic; we

never got an answer so I just changed the state to "offline".  

That's an argument for "test it anyway".  If it starts showing

consistently good results, we could change it back to "Active: yes".

Though feedback to "Are you having problems" questions is also good.


reported=2019-09-10 05:47:03

reporter=onefang

priority=normal

category=TODO

severity=minor

resolution=fixed


2019-12-01 19:24:57 onefang: Adding a * after OK or FAILED, and using a different shade for the web version.